Interfacing between a caller application and a service module

ABSTRACT

A method and associated system for interfacing between a caller application and a service module. Upon receiving a request for performing a transaction that includes at least one caller application attribute describing the request, the service module builds a service module data structure pursuant to the received request. The service module data structure includes a generic service document and at least one service module attribute. Each service module attribute is stored in a relational table of the service module data structure, which includes. The request is serviced within the service module data structure, resulting in instantiating the generic service document. The generic service document is returned to the caller application. Storing each service module attribute in the relational table includes: determining a category and a level of a first service module attribute; and storing in the relational table a first container pursuant to the category and the level.

This application is a continuation application claiming priority to Ser.No. 12/102,492, filed Apr. 14, 2008, now U.S. Pat. No. 8,286,186, issuedOct. 9, 2012.

FIELD OF THE INVENTION

The present invention discloses a system and associated method for adata interface that differentiates multiple caller applicationsrequesting a service of a commonly callable service application.

BACKGROUND OF THE INVENTION

A conventional service application that is shared by multiple callerapplications cannot extend a data model of a caller application in adata model of the conventional service application. Also, theconventional service application interferes with the data model of thecaller application in performing a service requested by the callerapplication. Also, the conventional service application uses a datainterface that may confuse identities of data elements of callerapplications. Thus, there is a need for a system and associated methodthat overcomes at least one of the preceding disadvantages of currentmethods and systems for a data interface of a shared serviceapplication.

SUMMARY OF THE INVENTION

The present invention provides a method for interfacing between a callerapplication and a service module, the method comprising:

receiving a request for performing a transaction from the callerapplication, wherein the request comprises at least one callerapplication attribute describing the transaction;

subsequent to said receiving, building a service module data structurepursuant to said received request, wherein the service module datastructure comprises a generic service document and at least one servicemodule attribute, wherein the service module uses only the servicemodule data structure such that the service module needs not manipulatesaid at least one caller application attribute in performing thetransaction;

subsequent to said building, storing each service module attribute ofsaid at least one service module attribute in a relational table of theservice module data structure;

subsequent to said storing, servicing the request within the servicemodule data structure, wherein said servicing results in instantiatingthe generic service document; and

subsequent to said servicing, returning the generic service document tothe caller application,

wherein said receiving, said building, said storing, said servicing, andsaid returning are performed by the service module.

The present invention provides a computer program product, comprising acomputer usable medium having a computer readable program code embodiedtherein, said computer readable program code containing instructionsthat when executed by a processor of a computer system implement amethod for interfacing between a caller application and a servicemodule, the method comprising:

receiving a request for performing a transaction from the callerapplication, wherein the request comprises at least one callerapplication attribute describing the transaction;

subsequent to said receiving, building a service module data structurepursuant to said received request, wherein the service module datastructure comprises a generic service document and at least one servicemodule attribute, wherein the service module uses only the servicemodule data structure such that the service module needs not manipulatesaid at least one caller application attribute in performing thetransaction;

subsequent to said building, storing each service module attribute ofsaid at least one service module attribute in a relational table of theservice module data structure;

subsequent to said storing, servicing the request within the servicemodule data structure, wherein said servicing results in instantiatingthe generic service document; and

subsequent to said servicing, returning the generic service document tothe caller application,

wherein said receiving, said building, said storing, said servicing, andsaid returning are performed by the service module.

The present invention provides a computer system comprising a processorand a computer readable memory unit coupled to the processor, saidmemory unit containing instructions that when executed by the processorimplement a method for interfacing between a caller application and aservice module, the method comprising:

receiving a request for performing a transaction from the callerapplication, wherein the request comprises at least one callerapplication attribute describing the transaction;

subsequent to said receiving, building a service module data structurepursuant to said received request, wherein the service module datastructure comprises a generic service document and at least one servicemodule attribute, wherein the service module uses only the servicemodule data structure such that the service module needs not manipulatesaid at least one caller application attribute in performing thetransaction;

subsequent to said building, storing each service module attribute ofsaid at least one service module attribute in a relational table of theservice module data structure;

subsequent to said storing, servicing the request within the servicemodule data structure, wherein said servicing results in instantiatingthe generic service document; and

subsequent to said servicing, returning the generic service document tothe caller application,

wherein said receiving, said building, said storing, said servicing, andsaid returning are performed by the service module.

The present invention provides a process for supporting computerinfrastructure, said process comprising providing at least one supportservice for at least one of creating, integrating, hosting, maintaining,and deploying computer-readable code in a computing system, wherein thecode in combination with the computing system is capable of performing amethod for interfacing between a caller application and a servicemodule, the method comprising:

receiving a request for performing a transaction from the callerapplication, wherein the request comprises at least one callerapplication attribute describing the transaction;

subsequent to said receiving, building a service module data structurepursuant to said received request, wherein the service module datastructure comprises a generic service document and at least one servicemodule attribute, wherein the service module uses only the servicemodule data structure such that the service module needs not manipulatesaid at least one caller application attribute in performing thetransaction;

subsequent to said building, storing each service module attribute ofsaid at least one service module attribute in a relational table of theservice module data structure;

subsequent to said storing, servicing the request within the servicemodule data structure, wherein said servicing results in instantiatingthe generic service document; and

subsequent to said servicing, returning the generic service document tothe caller application,

wherein said receiving, said building, said storing, said servicing, andsaid returning are performed by the service module.

The present invention provides a method and system that overcomes atleast one of the current disadvantages of conventional method and systemfor interfacing between a caller application and a shared servicemodule.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a shared service module data interface system, inaccordance with embodiments of the present invention.

FIG. 2 is a flowchart depicting a method for a common accounting moduledata interface system of FIG. 1, in accordance with the embodiments ofthe present invention.

FIG. 2A is a flowchart depicting a method for building up the CAM datastructure of FIG. 1, in accordance with the embodiments of the presentinvention.

FIG. 2B is a flowchart depicting a method for storing CAM attributes inthe CAM data structure of FIG. 1, in accordance with the embodiments ofthe present invention.

FIG. 2C is a flowchart depicting a method for servicing the request ofthe caller application, in accordance with the embodiments of thepresent invention.

FIG. 3 illustrates a computer system used for extensible data interfacefor a shared service module, in accordance with embodiments of thepresent invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a shared service module data interface system, inaccordance with embodiments of the present invention.

The shared service module data interface system comprises a callerapplication 110, a shared service module, and a shared service moduledata structure. The caller application 110 sends a request 120 to theshared service module for a transaction that is performed by the sharedservice module. In this embodiment, the shared service module datainterface system is a common accounting module (CAM) data interfacesystem 100, the shared service module is a common accounting module(CAM) 200, the shared service module data structure is a commonaccounting module (CAM) data structure 300, and the transaction is anaccounting service.

The CAM data structure 300 comprises a caller identifier 301, at leastone CAM attribute 310, a configuration table 320, at least one container330, a mapping table 340, a relational table 350, and a genericaccounting document 360.

The caller identifier 301 differentiates each caller application 110that requests an accounting service of the CAM 200. The calleridentifier 301 is configured by the CAM 200 and identifies all dataassociated with the caller application 110 within the CAM data structure300. Data that are specific to each caller application 110 are producedwhile the CAM 200 performs an accounting function according to therequest 120 from the caller application 110. Thus, a single webapplication instance of the CAM 200 concurrently provides accountingservices to multiple caller applications 110 that are uniquelyidentified by the caller identifier 301 through the CAM data interfacesystem 100.

In one embodiment of the present invention, the caller identifier 301 isstored in a variable InstAppl_Id that is included in a document header.In another embodiment, the caller identifier 301 is stored in anothervariable InstAppl_Id that is included in all data entities that arebuilt up to service a request 120 from the caller application 110 thatis identified by the caller identifier 301. The caller application 110provides a value of the caller identifier 301 to the CAM 200. Examplesof values of the caller identifier 301 include, inter alia, ‘APU001’,‘REQ001’, and ‘REQ002.’ Each example value of the caller identifier 301comprises an application number and a sequence number for a runninginstance. A pair of caller identifiers 301 ‘REQ001’ and ‘REQ002’ of theexample above represents that one caller application 110 that has theapplication number REQ has two running instances, and each of therunning instances is uniquely identified with the sequence numberfollowed by the application number, hence ‘REQ001’ and ‘REQ002’comprises respective caller identifier 301.

The CAM attribute 310 describes properties of the request 120 within theCAM data structure 300. The CAM attribute 310 is identified from therequest 120 and subsequently classified to service the request 120 fromthe caller application 110. The CAM attribute 310 comprises at least onepart key. If the CAM attribute 310 comprises more than one part key,each part key is separated by a delimiter. The CAM 200 maintains the CAMattribute 310 without manipulating the CAM attribute while servicing thetransaction requested by the caller application 110. Formats of the CAMattribute 310 may include, inter alia, a single column key, amulti-column key, etc. The single column key may be a unit data valuesuch as ‘AF34K1’ which identifies a single purchase request. Themulti-column key may be, for example, ‘631˜03˜420038688’ which is aseries of code representing hierarchical information of a purchase orderby an entity, as a country, a company, and a serial number of thepurchase order that has been made by the entity.

The configuration table 320 stores category and level information of allCAM attributes 310 that the CAM 200 needs to service the request 120 forthe caller application 110. The CAM attribute 310 is categorized as oneof two categories: a basic-category and an extended-category.Basic-category attributes are original to the caller application 110that requests the CAM 200 to perform a transaction. Both the callerapplication 110 and the CAM 200 recognize basic-category attributes.Extended-category attributes are, on the other hand, not recognized bythe CAM 200 without additional configuration. The CAM may recognizeextended-category attributes either by additional configuration or byencoding of specific accounting rules and associating the encoded ruleswith extended-category attributes. The CAM 200 data model need not bechanged in recognizing extended-category attributes as described above.Extended-category attributes may be defined for a specific entity thatmanipulates the requested accounting function. The CAM attribute 310 isalso divided into two levels, a header-level and an item-level,independent of a category of the CAM attribute 310. The header-levelattribute is applicable to all items in a service document with a headercomprising the header-level attribute. The item-level attribute isapplicable only to an item within a service document that is describedby the item-level attribute. Information on both the category and thelevel of a CAM attribute is collectively referred to as classificationinformation in this specification.

A container 330 is created within the generic accounting document 360for each CAM attribute 310 to hold a data value of an associated CAMattribute 310. Each container 330 is classified according to thecategory and the level information of a respective CAM attribute 310 forwhich the container 330 holds a data value.

The mapping table 340 comprises information regarding associationbetween each CAM attribute 310 and a respective container 330 thatcorresponds to each CAM attribute 310. See description of the mappingtable 340 in FIG. 2, infra.

The relational table 350 is a set of CAM attributes 310 in the CAM datastructure 300. The relational table 350 is classified as one of fourtables that store a respective CAM attribute 310 according to thecategory and the level information of the CAM attribute 310: a documentheader table that comprises basic-category and header-level attributes,a document item table that comprises basic-category and item-levelattributes, a document header extension table that comprisesextended-category and header-level attributes, and a document itemextension table that comprises extended-category and item-levelattributes.

The generic accounting document 360 comprises containers 330 and isreturned to the caller application 110 after servicing the request 120.

FIG. 2 is a flowchart depicting a method for a common accounting moduledata interface system of FIG. 1, supra, in accordance with theembodiments of the present invention.

In step 210, the common accounting module (CAM) receives a request foran accounting service from a caller application. Examples of theaccounting service may include, inter alia, a data collection, a datavalidation, a purchase, etc.

In step 220, the CAM builds up a relational table in the CAM datastructure comprising containers. See FIG. 2A, infra, for details.

In step 230, the CAM determines a storage location of each containerthat is a column and/or a row in the relational table built in step 220.

In step 240, the CAM stores a CAM attribute associated with the locatedcontainer from step 230. See FIG. 2B, infra, for details.

In step 250, the CAM determines if there is a container that does nothold a data value for an associated CAM attribute left unprocessed. Ifthe CAM determines that there is a container left unprocessed, the CAMloops back to step 230 and re-performs steps 230, 240, and 250. If theCAM determines that there are no more containers left, then the CAMproceeds with step 260.

In step 260, the CAM services the request from the caller application.See FIG. 2C, infra, for details.

FIG. 2A is a flowchart depicting a method for building up the CAM datastructure of FIG. 1, supra, in accordance with the embodiments of thepresent invention.

In step 2201, the CAM identifies and classifies attributes that arenecessary to the accounting process in the request. The CAM datainterface instantiates a configuration table in the CAM data structurewith item identity and classification information.

In step 2202, the CAM configures a caller identifier that is unique toeach caller application. The CAM differentiates transactional data ofone caller application from the other caller application with the calleridentifier. The caller identifier is used to compose the primary key ofall stored transactional data as to the service of the request.Consequently, the CAM may service multiple caller applications within aninstance without confusing identities of each caller application.

In step 2203, the CAM creates a generic accounting document whichrepresents the business transaction or purchasing document, parsing theinput stream and assembling the CAM data structure.

In step 2204, the CAM creates a container per CAM attribute, andattaches created containers to the generic accounting document. Thecontainer holds a data value of a corresponding CAM attribute. Thesecontainers hold the business data values. When each container iscreated, each container is associated with respective CAM attribute ineach mapping. All mapping is stored in a mapping table.

In step 2205, the CAM reads the mapping table and obtains names of CAMattributes. The CAM interface program assigns the CAM attribute names toeach container using the mapping table.

By using the mapping table, the method of the present invention candynamically extend a data structure in order to share existingapplication system data from multiple caller applications. A datastructure of the CAM, i.e., the CAM data structure, and a data structureof the caller application independently operate without exposingrespective data structure to each other. Two independent data structuresof the CAM and the caller application are associated by a name, aposition, and a combination of the name and the position, andinformation regarding this association is stored in the mapping table.

In one embodiment of the present invention, the CAM associates a dataelement of the caller application, i.e., an attribute, with a data itemof the CAM, i.e., a container, by a name. Respective data of the CAM andthe caller application are associated solely by the name of the data,without regarding a position of the data element by the CAM.

In another embodiment of the present invention, the CAM associates adata element of the caller application, i.e., an attribute, with a dataitem of the CAM, i.e., a container, by a position in a set of dataelements. Thus, the CAM uses the position of the data element in the setof data elements of the caller application in identifying the dataelement and locating storage of the data item as stored within the CAMdata structure. If no data element is named in the request of the callerapplication, the CAM maps all data elements by the position of the dataelement.

In still another embodiment of the present invention, the CAM associatesa data element of the caller application, i.e., an attribute, with adata item of the CAM, i.e., a container, by a name of the data elementand a position in a set of data elements. In the same embodiment, theCAM uses a name of the data element for some data elements incombination with the position to assure proper association of dataelements. For a named data element, a position of the named data elementis assumed to be honored for all data elements and the position of thenamed data element is checked by the CAM. If the named data element isnot in a defined position, then an unnamed data element is assumed to bein a correct position relative to the position of the named data elementwithin a set of data elements. If the named element is in the definedposition, then all data elements are handled by respective position.

FIG. 2B is a flowchart depicting a method for storing CAM attributes inthe CAM data structure of FIG. 1, supra, in accordance with theembodiments of the present invention.

Steps 2401 to 2407 are performed on each container located in step 230of FIG. 2, supra.

In step 2401, the CAM determines whether the container holds an extendedattribute by looking up the configuration table that comprisesclassification information, i.e., a category and a level, of CAMattributes. If the CAM determines that the container holds anextended-category attribute, the CAM proceeds with step 2402. If the CAMdetermines that the container does not hold an extended-categoryattribute, the CAM proceeds with step 2403.

In step 2402, the CAM determines whether the container is either aheader-level container or an item-level container. If the CAM determinesthat the container is a header-level container, the CAM proceeds withstep 2404. If the CAM determines that the container is an item-levelcontainer, the CAM proceeds with step 2405.

In step 2403, the CAM determines whether the container is either aheader level container or an item level container. If the CAM determinesthat the container is a header level container, the CAM proceeds withstep 2406. If the CAM determines that the container is an item levelcontainer, the CAM proceeds with step 2407.

In step 2404, because the CAM had determined that the container has anextended attribute in a header level container, the CAM stores thecontainer comprising a name and a value of the extended attribute as arow in a document extension data store that is designated to store anextended-header level container.

In step 2405, because the CAM had determined that the container has anextended attribute in an item level container, the CAM stores thecontainer comprising a name and a value of the extended attribute as arow in a document item extension data store that is designated to storean extended-item level container.

In step 2406, because the CAM had determined that the container has abasic attribute in a header level container, the CAM stores thecontainer comprising a value of the basic attribute as a column in adocument header table that is designated to store a basic-header levelcontainer.

In step 2407, because the CAM had determined that the container has abasic attribute in an item level container, the CAM stores the containercomprising a value of the basic attribute as a column in a document itemtable that is designated to store a basic-item level container.

After the CAM performs one of steps 2404, 2405, 2406, or 2407, the CAMproceeds with step 250 in FIG. 2, supra.

FIG. 2C is a flowchart depicting a method for servicing the request ofthe caller application, in accordance with the embodiments of thepresent invention.

In step 2601, the CAM performs the data validation or collection requestfrom the caller application as received in step 210 of FIG. 2, supra.

In step 2602, the CAM reads the mapping table to find outcontainer-attribute association and proper storage location for theattribute.

In step 2603, the CAM reloads accounting element types from data storeinto the generic document.

In step 2604, the CAM returns the generic document representing adocument and/or a transaction to the caller application. The genericdocument that is passed to the caller application is by a position and aname of each attribute to accommodate an attribute locating system ofthe caller application.

FIG. 3 illustrates a computer system 90 used for extensible datainterface for a shared service module, in accordance with embodiments ofthe present invention.

The computer system 90 comprises a processor 91, an input device 92coupled to the processor 91, an output device 93 coupled to theprocessor 91, and memory devices 94 and 95 each coupled to the processor91. The input device 92 may be, inter alia, a keyboard, a mouse, akeypad, a touchscreen, a voice recognition device, a sensor, a networkinterface card (NIC), a Voice/video over Internet Protocol (VOIP)adapter, a wireless adapter, a telephone adapter, a dedicated circuitadapter, etc. The output device 93 may be, inter alia, a printer, aplotter, a computer screen, a magnetic tape, a removable hard disk, afloppy disk, a NIC, a VOIP adapter, a wireless adapter, a telephoneadapter, a dedicated circuit adapter, an audio and/or visual signalgenerator, a light emitting diode (LED), etc. The memory devices 94 and95 may be, inter alia, a cache, a dynamic random access memory (DRAM), aread-only memory (ROM), a hard disk, a floppy disk, a magnetic tape, anoptical storage such as a compact disc (CD) or a digital video disc(DVD), etc. The memory device 95 includes a computer code 97 which is acomputer program that comprises computer-executable instructions. Thecomputer code 97 includes, inter alia, an algorithm used for extensibledata interface for the shared service module, according to the presentinvention. The processor 91 executes the computer code 97. The memorydevice 94 includes input data 96. The input data 96 includes inputrequired by the computer code 97. The output device 93 displays outputfrom the computer code 97. Either or both memory devices 94 and 95 (orone or more additional memory devices not shown in FIG. 3) may be usedas a computer usable medium (or a computer readable medium or a programstorage device) having a computer readable program embodied thereinand/or having other data stored therein, wherein the computer readableprogram comprises the computer code 97. Generally, a computer programproduct (or, alternatively, an article of manufacture) of the computersystem 90 may comprise said computer usable medium (or said programstorage device).

Any of the components of the present invention can be deployed, managed,serviced, etc. by a service provider that offers to deploy or integratecomputing infrastructure with respect to a process for extensible datainterface for the shared service module of the present invention. Thus,the present invention discloses a process for supporting computerinfrastructure, comprising integrating, hosting, maintaining anddeploying computer-readable code into a computing system (e.g.,computing system 90), wherein the code in combination with the computingsystem is capable of performing a method for extensible data interfacefor the shared service module,

In another embodiment, the invention provides a business method thatperforms the process steps of the invention on a subscription,advertising and/or fee basis. That is, a service provider, such as aSolution Integrator, can offer to create, maintain, support, etc. aprocess for extensible data interface for the shared service module ofthe present invention. In this case, the service provider can create,maintain, support, etc. a computer infrastructure that performs theprocess steps of the invention for one or more customers. In return, theservice provider can receive payment from the customer(s) under asubscription and/or fee agreement, and/or the service provider canreceive payment from the sale of advertising content to one or morethird parties.

While FIG. 3 shows the computer system 90 as a particular configurationof hardware and software, any configuration of hardware and software, aswould be known to a person of ordinary skill in the art, may be utilizedfor the purposes stated supra in conjunction with the particularcomputer system 90 of FIG. 3. For example, the memory devices 94 and 95may be portions of a single memory device rather than separate memorydevices.

While particular embodiments of the present invention have beendescribed herein for purposes of illustration, many modifications andchanges will become apparent to those skilled in the art. Accordingly,the appended claims are intended to encompass all such modifications andchanges as fall within the true spirit and scope of this invention.

The invention claimed is:
 1. A method for interfacing between a callerapplication and a service module, said method comprising: receiving, bya processor of a computer system, a request for performing a transactionfrom the caller application, wherein the request comprises at least onecaller application attribute describing the request; subsequent to saidreceiving, said processor building a service module data structurepursuant to the received request, wherein the service module datastructure comprises a generic service document and at least one servicemodule attribute, wherein the service module uses only the servicemodule data structure such that the service module need not manipulatethe at least one caller application attribute in performing thetransaction; subsequent to said building, said processor storing eachservice module attribute of the at least one service module attribute ina relational table of the service module data structure; subsequent tosaid storing, said processor servicing the request within the servicemodule data structure, wherein said servicing results in instantiatingthe generic service document; and subsequent to said servicing, saidprocessor returning the generic service document to the callerapplication; said service module being executed by the processor toperform said receiving the request, said building the service moduledata structure, said storing each service module attribute, saidservicing the request, and said returning the generic service document;said storing comprising: determining a category of a first servicemodule attribute of the at least one service module attribute, wherein aconfiguration table comprises a respective category of each servicemodule attribute, wherein the category is either an extended-categorythat is recognized only by the caller application or a basic-categorythat is recognized by both the caller application and the servicemodule; subsequent to said determining the category, determining a levelof the first service module attribute, wherein the configuration tablefurther comprises a respective level of each service module attribute,wherein the level is either a header-level that is applicable for allservice module attributes represented in the generic service document oran item-level that is applicable only for the first service moduleattribute; subsequent to said determining the level, storing in therelational table a first container of at least one container, said firstcontainer being pursuant to the category and the level of the firstservice module attribute that is associated with the first container,wherein the relational table is selected from the group consisting of afirst table for service module attributes determined to be in thebasic-category and in the header-level, a second table for servicemodule attributes determined to be in the basic-category and in theitem-level, a third table for service module attributes determined to bein the extended-category and in the header-level, and a fourth table forservice module attributes determined to be in the extended-category andin the item-level; and subsequent to said storing the first container,repeating to perform said determining the category, said determining thelevel, and said storing the first container after setting the firstcontainer with a next container in the relational table until allcontainers are stored in the relational table.
 2. The method of claim 1,said building comprising: defining the at least one service moduleattribute of the service module data structure, wherein each servicemodule attribute of the at least one service module attribute eithercorresponds to one caller application attribute of the at least onecaller application attribute or is created by the service module;subsequent to said defining, configuring a caller identifier thatuniquely identifies the caller application and the service module datastructure pursuant to the received request; subsequent to saidconfiguring, constructing the generic service document, wherein thegeneric service document is configured to contain a result of theperformed transaction; subsequent to said constructing, creating one ormore containers in the generic service document, wherein each containerof the one or more containers is respectively associated with eachservice module attribute in each mapping of at least one mapping in amapping table of the service module data structure, wherein eachcontainer comprises a data value for each service module attribute ofthe at least one service module attribute; and subsequent to saidcreating, naming each container of the one or more containers in thegeneric service document after each mapping of the at least one mappingin the mapping table.
 3. The method of claim 1, said servicingcomprising: performing the transaction; subsequent to said performingthe transaction, retrieving each mapping from a mapping table of theservice module data structure; and subsequent to said retrieving,reloading each container of the at least one container from therelational table into respective containers of the generic servicedocument according to each retrieved mapping.
 4. The method of claim 1,wherein the caller application is a member of a group comprising atleast two caller applications, and wherein the service module is sharedby each member of the group.
 5. A computer program product, comprising acomputer readable storage device having computer readable program codestored therein, said program code configured to be executed by aprocessor of a computer system to implement a method for interfacingbetween a caller application and a service module, said methodcomprising: said processor receiving a request for performing atransaction from the caller application, wherein the request comprisesat least one caller application attribute describing the request;subsequent to said receiving, said processor building a service moduledata structure pursuant to the received request, wherein the servicemodule data structure comprises a generic service document and at leastone service module attribute, wherein the service module uses only theservice module data structure such that the service module need notmanipulate the at least one caller application attribute in performingthe transaction; subsequent to said building, said processor storingeach service module attribute of the at least one service moduleattribute in a relational table of the service module data structure;subsequent to said storing, said processor servicing the request withinthe service module data structure, wherein said servicing results ininstantiating the generic service document; and subsequent to saidservicing, said processor returning the generic service document to thecaller application; said service module being executed by the processorto perform said receiving the request, said building the service moduledata structure, said storing each service module attribute, saidservicing the request, and said returning the generic service document;said storing comprising: determining a category of a first servicemodule attribute of the at least one service module attribute, wherein aconfiguration table comprises a respective category of each servicemodule attribute, wherein the category is either an extended-categorythat is recognized only by the caller application or a basic-categorythat is recognized by both the caller application and the servicemodule; subsequent to said determining the category, determining a levelof the first service module attribute, wherein the configuration tablefurther comprises a respective level of each service module attribute,wherein the level is either a header-level that is applicable for allservice module attributes represented in the generic service document oran item-level that is applicable only for the first service moduleattribute; subsequent to said determining the level, storing in therelational table a first container of at least one container, said firstcontainer being pursuant to the category and the level of the firstservice module attribute that is associated with the first container,wherein the relational table is selected from the group consisting of afirst table for service module attributes determined to be in thebasic-category and in the header-level, a second table for servicemodule attributes determined to be in the basic-category and in theitem-level, a third table for service module attributes determined to bein the extended-category and in the header-level, and a fourth table forservice module attributes determined to be in the extended-category andin the item-level; and subsequent to said storing the first container,repeating to perform said determining the category, said determining thelevel, and said storing the first container after setting the firstcontainer with a next container in the relational table until allcontainers are stored in the relational table.
 6. The computer programproduct of claim 5, said building comprising: defining the at least oneservice module attribute of the service module data structure, whereineach service module attribute of the at least one service moduleattribute either corresponds to one caller application attribute of theat least one caller application attribute or is created by the servicemodule; subsequent to said defining, configuring a caller identifierthat uniquely identifies the caller application and the service moduledata structure pursuant to the received request; subsequent to saidconfiguring, constructing the generic service document, wherein thegeneric service document is configured to contain a result of theperformed transaction; subsequent to said constructing, creating one ormore containers in the generic service document, wherein each containerof the one or more containers is respectively associated with eachservice module attribute in each mapping of at least one mapping in amapping table of the service module data structure, wherein eachcontainer comprises a data value for each service module attribute ofthe at least one service module attribute; and subsequent to saidcreating, naming each container of the one or more containers in thegeneric service document after each mapping of the at least one mappingin the mapping table.
 7. The computer program product of claim 5, saidservicing comprising: performing the transaction; subsequent to saidperforming the transaction, retrieving each mapping from a mapping tableof the service module data structure; and subsequent to said retrieving,reloading each container of the at least one container from therelational table into respective containers of the generic servicedocument according to each retrieved mapping.
 8. The computer programproduct of claim 5, wherein the caller application is a member of agroup comprising at least two caller applications, and wherein theservice module is shared by each member of the group.
 9. A computersystem comprising a processor, a memory coupled to the processor, and acomputer readable storage device coupled to the processor, said storagedevice containing program code configured to be executed by theprocessor via the memory to implement a method for interfacing between acaller application and a service module, said method comprising: saidprocessor receiving a request for performing a transaction from thecaller application, wherein the request comprises at least one callerapplication attribute describing the request; subsequent to saidreceiving, said processor building a service module data structurepursuant to the received request, wherein the service module datastructure comprises a generic service document and at least one servicemodule attribute, wherein the service module uses only the servicemodule data structure such that the service module need not manipulatethe at least one caller application attribute in performing thetransaction; subsequent to said building, said processor storing eachservice module attribute of the at least one service module attribute ina relational table of the service module data structure; subsequent tosaid storing, said processor servicing the request within the servicemodule data structure, wherein said servicing results in instantiatingthe generic service document; and subsequent to said servicing, saidprocessor returning the generic service document to the callerapplication; said service module being executed by the processor toperform said receiving the request, said building the service moduledata structure, said storing each service module attribute, saidservicing the request, and said returning the generic service document;said storing comprising: determining a category of a first servicemodule attribute of the at least one service module attribute, wherein aconfiguration table comprises a respective category of each servicemodule attribute, wherein the category is either an extended-categorythat is recognized only by the caller application or a basic-categorythat is recognized by both the caller application and the servicemodule; subsequent to said determining the category, determining a levelof the first service module attribute, wherein the configuration tablefurther comprises a respective level of each service module attribute,wherein the level is either a header-level that is applicable for allservice module attributes represented in the generic service document oran item-level that is applicable only for the first service moduleattribute; subsequent to said determining the level, storing in therelational table a first container of at least one container, said firstcontainer being pursuant to the category and the level of the firstservice module attribute that is associated with the first container,wherein the relational table is selected from the group consisting of afirst table for service module attributes determined to be in thebasic-category and in the header-level, a second table for servicemodule attributes determined to be in the basic-category and in theitem-level, a third table for service module attributes determined to bein the extended-category and in the header-level, and a fourth table forservice module attributes determined to be in the extended-category andin the item-level; and subsequent to said storing the first container,repeating to perform said determining the category, said determining thelevel, and said storing the first container after setting the firstcontainer with a next container in the relational table until allcontainers are stored in the relational table.
 10. The computer systemof claim 9, said building comprising: defining the at least one servicemodule attribute of the service module data structure, wherein eachservice module attribute of the at least one service module attributeeither corresponds to one caller application attribute of the at leastone caller application attribute or is created by the service module;subsequent to said defining, configuring a caller identifier thatuniquely identifies the caller application and the service module datastructure pursuant to the received request; subsequent to saidconfiguring, constructing the generic service document, wherein thegeneric service document is configured to contain a result of theperformed transaction; subsequent to said constructing, creating one ormore containers in the generic service document, wherein each containerof the one or more containers is respectively associated with eachservice module attribute in each mapping of at least one mapping in amapping table of the service module data structure, wherein eachcontainer comprises a data value for each service module attribute ofthe at least one service module attribute; and subsequent to saidcreating, naming each container of the one or more containers in thegeneric service document after each mapping of the at least one mappingin the mapping table.
 11. The computer system of claim 9, said servicingcomprising: performing the transaction; subsequent to said performingthe transaction, retrieving each mapping from a mapping table of theservice module data structure; and subsequent to said retrieving,reloading each container of the at least one container from therelational table into respective containers of the generic servicedocument according to each retrieved mapping.
 12. The computer system ofclaim 9, wherein the caller application is a member of a groupcomprising at least two caller applications, and wherein the servicemodule is shared by each member of the group.
 13. A process forsupporting computer infrastructure, said process comprising providing atleast one support service for at least one of creating, integrating,hosting, maintaining, and deploying computer-readable code in a computersystem, wherein the code in combination with the computer system isconfigured to perform a method for interfacing between a callerapplication and a service module, said method comprising: receiving, bya processor of the computer system, a request for performing atransaction from the caller application, wherein the request comprisesat least one caller application attribute describing the request;subsequent to said receiving, said processor building a service moduledata structure pursuant to the received request, wherein the servicemodule data structure comprises a generic service document and at leastone service module attribute, wherein the service module uses only theservice module data structure such that the service module need notmanipulate the at least one caller application attribute in performingthe transaction; subsequent to said building, said processor storingeach service module attribute of the at least one service moduleattribute in a relational table of the service module data structure;subsequent to said storing, said processor servicing the request withinthe service module data structure, wherein said servicing results ininstantiating the generic service document; and subsequent to saidservicing, said processor returning the generic service document to thecaller application; said service module being executed by the processorto perform said receiving the request, said building the service moduledata structure, said storing each service module attribute, saidservicing the request, and said returning the generic service document;said storing comprising: determining a category of a first servicemodule attribute of the at least one service module attribute, wherein aconfiguration table comprises a respective category of each servicemodule attribute, wherein the category is either an extended-categorythat is recognized only by the caller application or a basic-categorythat is recognized by both the caller application and the servicemodule; subsequent to said determining the category, determining a levelof the first service module attribute, wherein the configuration tablefurther comprises a respective level of each service module attribute,wherein the level is either a header-level that is applicable for allservice module attributes represented in the generic service document oran item-level that is applicable only for the first service moduleattribute; subsequent to said determining the level, storing in therelational table a first container of at least one container, said firstcontainer being pursuant to the category and the level of the firstservice module attribute that is associated with the first container,wherein the relational table is selected from the group consisting of afirst table for service module attributes determined to be in thebasic-category and in the header-level, a second table for servicemodule attributes determined to be in the basic-category and in theitem-level, a third table for service module attributes determined to bein the extended-category and in the header-level, and a fourth table forservice module attributes determined to be in the extended-category andin the item-level; and subsequent to said storing the first container,repeating to perform said determining the category, said determining thelevel, and said storing the first container after setting the firstcontainer with a next container in the relational table until allcontainers are stored in the relational table.
 14. The process of claim13, said building comprising: defining the at least one service moduleattribute of the service module data structure, wherein each servicemodule attribute of the at least one service module attribute eithercorresponds to one caller application attribute of the at least onecaller application attribute or is created by the service module;subsequent to said defining, configuring a caller identifier thatuniquely identifies the caller application and the service module datastructure pursuant to the received request; subsequent to saidconfiguring, constructing the generic service document, wherein thegeneric service document is configured to contain a result of theperformed transaction; subsequent to said constructing, creating one ormore containers in the generic service document, wherein each containerof the one or more containers is respectively associated with eachservice module attribute in each mapping of at least one mapping in amapping table of the service module data structure, wherein eachcontainer comprises a data value for each service module attribute ofthe at least one service module attribute; and subsequent to saidcreating, naming each container of the one or more containers in thegeneric service document after each mapping of the at least one mappingin the mapping table.
 15. The process of claim 13, said servicingcomprising: performing the transaction; subsequent to said performingthe transaction, retrieving each mapping from a mapping table of theservice module data structure; and subsequent to said retrieving,reloading each container of the at least one container from therelational table into respective containers of the generic servicedocument according to each retrieved mapping.
 16. The process of claim13, wherein the caller application is a member of a group comprising atleast two caller applications, and wherein the service module is sharedby each member of the group.